gDEBugger User Guide
| gDEBugger User Guide |
The OpenGL Calls History Toolbar lets you access the Calls History Commands.
The Context Combo Box allows you to choose the context displayed in the OpenGL Function Calls History view.
Start / stop recording the OpenGL calls log to a file.
The files are recorded to the directory as defined in the Debug Settings dialog.
Display log file û Open the the active context recorded HTML log file.
Scroll the OpenGL Calls History View to the next string marker function call.
Scroll the OpenGL Calls History View to the previous string marker function call.
String markers are text messages that can be embedded in the OpenGL calls history log of your application. This is done by using the GL_GREMEDY_string_marker OpenGL extension.
String markers help you make the OpenGL calls history log more readable: you can mark any logical operation / section executed by your application with a marker string.
glStringMarkerGREMEDY(17, "Setting up lights");
glStringMarkerGREMEDY(20, "Drawing object no 10");
The use of the OpenGL extensions mechanism enables you to add, permanently, the string markers code into your source code. This code will be activated only when you run your application with gDEBugger.
You can put a breakpoint on the glStringMarkerGREMEDY function. This allows you to break the application run before it starts to execute the next marked logical operation / section.